Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Logged information

Event logging records information about the following types of actions as they apply to an event:

Event occurs — Either the client receives notification of an external event or the OpenEdge 4GL executes an APPLY statement.
Indirect action taken — The client takes additional action in response to the event. For example, on a Windows minimize event, the client might minimize several other related windows.
OpenEdge event pushed onto stack — The internal events that result from external events, such as LEAVE and ENTRY, are pushed onto the stack, from where they will be executed in sequence.
Event popped from stack without executing — In certain cases, OpenEdge does not execute events on the stack. For example:
An event occurs to a object that is disabled. OpenEdge pushes the event onto the stack, and then pops it off the stack without executing the corresponding trigger, if one exists.
Other examples: a trigger executes a RETURN NO-APPLY statement; a COM event occurs during a database or socket operation; a field’s validation fails.
Trigger started — Begins execution of the user interface trigger associated with the event.
Event applied by APPLY statement — OpenEdge logs each execution of an APPLY statement by a 4GL program. Frequently, an application calls an APPLY statement from within a user-defined trigger.
Trigger finished — Ends execution of the user interface trigger associated with the event.
Event popped off stack — Concludes a specific event execution.

The order of actions presented here is typical of what might appear in a log. Note, however, that not all actions occur for every event. An external event starts all of the actions that occur in an event-driven program, except for initialization. Thus, you would always expect to find in the log:

A GUI, socket, Async, or COM event first.
One or more OpenEdge events and their associated triggers or event procedures.
The conclusion of the external event.

Table 6–3 lists the information that is logged for each of the described actions. Note that the term object refers to the object that the event applies to.

Table 6–3: Information logged for each type of action

Action	Information logged
Event occurs.	Event Type — GUI (GUI Windows), UI (character mode), Socket, Async, COM, OpenEdge. Event Name — (For example) WM_xxx, OCX event name, LEAVE, TAB. Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available. Flag — Can be set to TRUE or FALSE for COM events (for use by Progress Software Corporation Technical Support). “OpenEdge Handled” — WM_ events for COM objects only. Logging this string means that OpenEdge captured the event and will process it, as opposed to passing it to the ActiveX control.
Indirect action.	Description — A descriptive string. When processing an event, OpenEdge might perform additional tasks that also will be recorded. These extra tasks include: minimize, restore, close related windows.
OpenEdge event pushed onto stack.	Event Name — (For example) LEAVE, ENTRY. Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available. Procedure Name — Name of the procedure that created the object. Note: OpenEdge makes no entry for COM events sent by an ActiveX control.
Event popped off stack without executing.	Event Name — (For example) LEAVE. Event Discarded — Noted as “discarded.” Additional information provided, if the reason for the action is known (for example, “disabled”). Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available.
Trigger started.	Handler — Event name and object name (similar to the ON statement), or name of the internal procedure.
Event applied by APPLY statement.	Event Name — (For example) ENTRY. Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available. Routine and line number — Name and line number of the routine (.p or .w file or method) and internal procedure, if appropriate, where the APPLY statement is. The line number is based on the Debugger listing file.
Trigger finished.	Handler — Event name and object name (similar to the ON statement), or name of the internal procedure.
Event popped off stack.	Event Name — (For example) LEAVE, ENTRY. Widget information — Type (BUTTON, for example), name, and handle ID of the object, when available. Routine Name — Name of the routine (.p or .w file or method) that created the object. Note: OpenEdge makes no entry for COM events sent by the control.